Step 01 — On the Skill page
Copy the PRD UX Analysis Skill
Go to the Skill page and copy the full prompt from "The Skill" section. That's the instruction set Claude will use to analyse whatever you give it.
Step 02 — On this page
Copy this transcript + add the modifier
Hit "Copy transcript" below. Because this is an interview, not a formal PRD, prepend this modifier before the Skill when you paste into Claude:
The following is a stakeholder interview transcript, not a PRD. Extract the implied requirements, then run the UX Analysis on what you extracted. Flag where requirements are inferred vs. explicitly stated.
Step 03 — In Claude
Run the analysis, compare the output
Open claude.ai or Claude Projects, paste in order: modifier → Skill → transcript. Claude will produce a full six-section UX Analysis. After reading the output, compare it to the gap list at the bottom of this page to see what it found.
The Interview
Credit Analyst Hub — Product Discovery
A 30-minute discovery session with a product manager and a lead credit analyst. This interview was conducted before any design work began — the kind of brief a designer might actually receive. It has the detail and the gaps of a real session.
Sarah — UX Designer (interviewer)
Sam — Lead Credit Analyst (end user)
Marcus — Product Manager
Part 1 — Current workflow
Sarah
UX Design
Thanks for making time. Before we get into specifics — Sam, can you walk me through what a typical morning looks like? What are you doing the moment you sit down?
Sam
Analyst
The first thing I do is check email. Honestly, that's where everything lives right now. I'm looking for anything from loan applicants about missing documents, anything from the risk committee about policy updates, and if I have a portfolio review coming up I'm trying to figure out if everything's in order.
Sarah
UX Design
What does "in order" mean for a monitoring visit?
Sam
Analyst
A Compliance Officer is going to come in and review source documents against what's in the system. I need to make sure every loan application that's due for a document review actually has its documents submitted, and any flags from the last review are resolved. Right now I track all of that in a spreadsheet. It's not — it's not great.
Marcus
Product
That spreadsheet is exactly what we're trying to replace. The goal is to give Sam one place where she can see which loan applications need attention, what's coming up in the next two weeks, and what's already overdue.
Part 2 — Patient management
Sarah
UX Design
When you say "applications that need attention" — what does that actually mean? What puts an application into that category?
Sam
Analyst
It could be a lot of things. A decision deadline that's closing — a loan application has a decision due within a certain timeframe and it's getting close. Or an applicant we tried to contact and couldn't reach. Or credit reports that came back flagged and need a Risk Manager to review. Or a compliance exception we need to document.
Sarah
UX Design
Those sound like very different levels of urgency. Are they weighted differently in your mind?
Sam
Analyst
Yes, definitely. A closing visit window is urgent in a way that an unreviewed lab result might not be. But right now everything is mixed together in email and I can't really triage.
Marcus
Product
We're thinking about a priority system — red for urgent, amber for follow-up needed, green for on track. We haven't fully worked out what triggers each level yet.
Sarah
UX Design
How many loan applications would a credit analyst typically be managing at once?
Sam
Analyst
Depends on the portfolio. Anywhere from 10 to 40 applications across one or two loan programs, sometimes three if they're smaller portfolios.
Sarah
UX Design
What do you need to see at a glance for each loan application?
Sam
Analyst
Their ID — we go by application ID rather than name for privacy reasons. Their current status in the review process. When their decision deadline is. And whether there's anything flagged on their record.
Sarah
UX Design
What statuses does a loan application move through over the review process?
Sam
Analyst
Top-level: submitted, under review, approved, funded, withdrawn. But there are sub-statuses too — an application could be under review but on a documentation hold, or under review with a potential compliance exception flag open against it. There's nuance there that matters.
Marcus
Product
For v1 we were thinking just the top-level statuses in the list view. The sub-status detail lives inside the application record.
Part 3 — Patient record and actions
Sarah
UX Design
What does clicking into an application record need to show you?
Sam
Analyst
Visit history — every visit they've had, what happened, any source document notes. Their upcoming visit schedule. And any open items: queries, flags, outstanding labs.
Sarah
UX Design
Is the record mostly read-only, or are there actions you'd need to take from there?
Sam
Analyst
You'd definitely take actions from there. Log a contact attempt — if I called an applicant and they didn't answer I need to record that. And send a reminder — if a decision deadline is coming up in a week I might want to send the applicant a reminder.
Sarah
UX Design
When you say "send a reminder" — what does that actually look like from the applicant's end?
Sam
Analyst
Right now I send an email. Sometimes I call. Some applicants prefer texts. I guess whatever the system supports — I'm not really sure what's technically possible here.
Sarah
UX Design
Can analysts schedule review meetings directly from within this tool?
Marcus
Product
That's a phase two feature. For v1 we want visibility only. Scheduling stays in the existing system.
Part 4 — Monitoring visit preparation
Sarah
UX Design
Let's talk about compliance review prep. You said you need to be ready before the Compliance Officer arrives — what does "ready" look like, concretely?
Sam
Analyst
I need to know which applications are going to be reviewed during the visit, which supporting documents are still outstanding, and whether any compliance exceptions are documented but not yet submitted. The Compliance Officer will also want to see the authorization log is up to date, but that's usually something the Risk Manager handles.
Sarah
UX Design
What's the authorization log?
Sam
Analyst
It's a record of everyone on the lending team and what they're each authorized to do. I can review applications and enter data, but I can't approve credit exceptions — that's the Risk Manager or branch manager. It needs to be current before every compliance review.
Marcus
Product
We're not building the authorization log into v1. But the tool does need to handle different user roles — a Credit Analyst sees one view, the Risk Manager sees something different, and a Compliance Officer doing a review visit should have a read-only view of the analyst's perspective.
Sarah
UX Design
What specifically does the Risk Manager need to see that a Credit Analyst doesn't?
Marcus
Product
We haven't fully worked that out yet. Probably medical assessments and any queries that require physician sign-off. We'll figure out the exact permission matrix in a follow-up session.
Part 5 — Users, access, and success
Sarah
UX Design
How many people would typically be using this at a single site?
Sam
Analyst
On a medium-sized portfolio — two or three credit analysts, one Risk Manager, maybe a branch manager. Then the Compliance Officer comes in roughly once a month for a review.
Sarah
UX Design
Does this need to work on mobile?
Sam
Analyst
I'm almost always at my desk when I'm doing this work. But occasionally I'll check something at the branch when I'm not at my desk — like if an applicant comes in and I need to quickly pull their record to confirm a decision deadline.
Marcus
Product
Desktop-first, definitely. But it needs to be at least functional on a phone for those situations.
Sarah
UX Design
Last question — what does success look like? If this tool is working in six months, what's different about your day?
Sam
Analyst
I wouldn't start my day in email. I'd open the dashboard and in under two minutes I'd know what needs my attention today, what's coming up this week, and whether I'm ready for any upcoming monitoring visits. Right now I spend the first hour of every morning just figuring out where I stand. That hour is completely wasted.
After you run the Skill
These are the gaps that were deliberately left open in this transcript. Run the Skill first — then come back and compare. If the analysis surfaces these issues (and others), it's doing its job.
Undefined triggerThe red/amber/green priority system has no defined threshold — "we haven't fully worked out what triggers each level" leaves the designer with no criteria to design against.
Missing channelThe applicant reminder action has no specified delivery mechanism — email, SMS, push, call — leaving a core interaction undefined.
Role permissionsRisk Manager vs. Credit Analyst access is explicitly deferred ("we'll figure out the exact permission matrix in a follow-up session"). The Compliance Officer read-only scope is described loosely but not specified.
Undefined thresholdVisit window "closing" is never defined — how many days before the protocol deadline does a visit become urgent? This drives the entire priority system.
Sub-status designSub-statuses (documentation hold, compliance exception open) are acknowledged as meaningful but deferred to "the application record" without any design discussion.
Mobile scope"Functional on a phone" is never defined — which actions, which views, what level of fidelity.
No error statesNo discussion of what happens when data fails to load, a save fails, or the connection drops mid-session.
No empty statesA new portfolio with no submitted applications, an analyst with no flagged items, a compliance review with no outstanding documents — none of these zero-data states are mentioned.
Contact attemptWhat fields are required when logging a contact attempt? What happens after multiple failed attempts? Is there an escalation path?
Using this as a starting point for your own Skills
This transcript is also an example of how Claude can help you build Skills and briefs from scratch. Rather than writing a PRD from nothing, try describing the app you're designing to Claude and ask it to generate a discovery interview — then use that as your Skill input. The same applies to Skills themselves: describe the analysis you need and ask Claude to draft the instruction set. Start with a conversation, not a blank page.